Resource reservation protocol based guaranteed quality of service internet protocol connections over a switched network through proxy signaling

ABSTRACT

A system and method establish an Internet protocol (IP) connection between an originating end-system and a destination end-system, incapable of resource reservation protocol (RSVP) signaling, through a switched transport network. A first interworking function (IWF) device inserts its switched transport network address into a first data field of an RSVP path message, received from an RSVP capable proxy signaling device that interfaces with the destination end-system. The first IWF device forwards the path message, through routers in an IP network, which is passed without modification to the first data field. A second IWF device receives the path message and forwards a setup message to the first IWF device through switching devices in the switched transport network, based on the first IWF device&#39;s address retrieved from the first data field of the path message. The IP connection is established through the proxy signaling device in response to the setup message.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application incorporates by reference in their entireties thedisclosures of the following applications, filed concurrently: “ResourceReservation Protocol Based Guaranteed Quality of Service InternetProtocol Connections over a Switched Network,” patent application Ser.No. 10/207,886; Resource Reservation Protocol Based Guaranteed Qualityof Service Internet Protocol (IP) Connections Over a Switched Networkusing Newly Assigned IP Addresses,” patent application Ser. No.10/207,880, now issued U.S. Pat. No. 7,065,092; and “Enhancement ofResource Reservation Protocol Enabling Short-Cut Internet ProtocolConnections over a Switched Network,” patent application Ser. No.10/207,905.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to the field of telecommunications. Moreparticularly, the present invention relates to establishing broadbandInternet protocol (IP) connections over a switched network, capable ofguaranteeing desired connection parameters, based on resourcereservation protocol (RSVP) signaling.

2. Acronyms

The written description provided herein contains acronyms which refer tovarious telecommunications services, components and techniques, as wellas features relating to the present invention. Although some of theseacronyms are known, use of these acronyms is not strictly standardizedin the art. For purposes of the written description herein, the acronymsare defined as follows:

-   Address Resolution Protocol (ARP)-   Asynchronous Transfer Mode (ATM)-   Constraint-Based Routed Label Distribution Protocol (CR-LDP)-   Digital Subscriber Line (DSL)-   Domain Naming System (DNS)-   Dynamic Host Configuration Protocol (DHCP)-   Generalized Multi-Protocol Label Switching (GMPLS)-   Internet Protocol (IP)-   Internet Service Provider (ISP)-   Interworking Function (IWF)-   Last-In-First-Out (LIFO)-   Local Area Network (LAN)-   Local IP Subnet (LIS)-   Multiple Address Resolution Server (MARS)-   Multi-Protocol Label Switching (MPLS)-   Network Service Access Point (NSAP)-   Next Hop Resolution Protocol (NHRP)-   Next Hop Server (NHS)-   Non-Broadcasting Multiple Access (NBMA)-   Permanent Virtual Circuit (PVC)-   Private Network-to-Network Interface (PNNI)-   Resource Reservation Protocol (RSVP)-   Quality of Service (QoS)-   Request for Comment (RFC)-   Switched Virtual Circuit (SVC)-   Time Division Multiplex (TDM)-   Transmission Control Protocol (TCP)-   Universal Resource Locator (URL)-   User Datagram Protocol (UDP)-   User Network Interface (UNI)-   User-to-User Information Element (UU IE)-   Virtual Channel Identifier (VCI)-   Virtual Path Identifier (VPI)-   Virtual Private Network (VPN)-   Wide Area Network (WAN)

BACKGROUND AND MATERIAL INFORMATION

With the development of various communications applications for use overpacket switched data networks, such as the Internet, demands forpredictable bandwidth and delay support are increasing. For example,services including voice-over-Internet and real-time audio, audio-visualand white-board conferencing, require the packets of transmitted data toarrive at a destination terminal with minimal delay and in a presentableorder.

Packet switched data networks generally support “best effort” routing ofdata. The packets of information sent from an originating end-system,such as an Internet subscriber, to a destination end-system, such as anInternet service provider (ISP), are transmitted through a network ofinterconnected routers using Internet protocol (IP). The IP networkessentially divides the transmitted data into packets, each of whichtravels to the destination end-system through a uniquely determined pathamong the available routers. The flow of a packet from one router to thenext router in the IP network is called a “hop.” The destinationend-system ultimately receives the packets and assembles them in theappropriate order to present the transmitted information.

Best effort routing is very flexible in that the data packets travelthrough any available combination of routers to ultimately reach thedestination end-system. When a router becomes unavailable, for example,due to traffic congestion causing its queue threshold to be exceeded,the data packets simply proceed through a different path. A disadvantageof best effort routing is that the speed and quality of the IP trafficis inconsistent due to packets being delayed, lost and received out oforder. In typical data transfer scenarios, this disadvantage may beinsignificant, especially when additional protocols, such astransmission control protocol/Internet protocol (TCP/IP) and userdatagram protocol/Internet protocol (UDP/IP), are implemented to resendand otherwise minimize the effect of lost and delayed data packets.However, many evolving applications depend on consistent and reliabledata packet routing, such as those applications involving real-timestreaming of audio and/or visual data.

The network criteria, such as bandwidth, needed for the IP network tosupport these applications are set forth in the quality of service (QoS)parameters. Generally, best effort routing cannot guarantee a particularQoS, especially when a large bandwidth is needed. Differential servicesmay be available in some IP networks. Differential services push asidelower priority traffic to accommodate a predetermined QoS fortransmissions of select subscribers, based on a preferred differentiallevel indicator in the data packet headers. However, differentialservices do not guarantee the desired level of service.

An IP network may also be implemented in conjunction with anon-broadcasting multiple access (NBMA) switched network, such as anasynchronous transfer mode (ATM) network, which is able to set asidecommunication paths that meet the predefined traffic requirements of thespecific applications. For example, an ATM network may set up and teardown a switched virtual circuit (SVC) of a specified bandwidth inresponse to dynamic communication demands on a per connection basis. TheIP network interfaces with a switched network according to variousmutually recognized protocols, such as resource reservation protocol(RSVP) and next hop resolution protocol (NHRP). Because the switchednetwork is typically able to isolate or reserve a particular route forthe duration of a connection, the required QoS may be established uponconnection to the network, accommodating predetermined parameters suchas delay, delay jitter and error rate, as well as the demands of theapplication and the state of the network at the time of connection.

RSVP is a network control protocol that enables QoS connections to beestablished and maintained by dynamically allocating bandwidth. RSVP isreceiver initiated in that the destination end-system initiates theactual reservation of resources or routing elements that enable theconnection. When the IP network is implemented over an ATM network, theIP addresses of the routing elements are translated into ATM addressesby a central server or database. The flow may then pass through theswitched network by setting up virtual circuits among ATM switches.

NHRP is an address resolution protocol that enables an IP end-system tointerface with a switching network, such as an ATM network, and connectwith another IP end-system. Use of NHRP extends address resolutionbetween networks across IP subnets. An originating end-system requests aconnection through routers in an IP network to a desired destinationend-system. A next hop server (NHS) maps the IP address of thedestination end-system to its associated ATM address using mapping dataand directs the routers to the next hop router in the IP network, untilthe connection request reaches the destination end-system. Generally,NHRP is not capable of supporting multicast communications.

Although conventional RSVP and NHRP generally enable IP connections overswitched networks, they are relatively cumbersome to implement. Bothprotocols require accessing a central mapping server or database, suchas an address resolution protocol (ARP) server or an NBMA-IP server, toassociate IP addresses with the corresponding NBMA switched networkaddresses, and to otherwise control the routing. Each device mustregister its IP address and NBMA address in the server, which resolvesthe IP addresses to the registered ATM addresses in response toconnection requests. Furthermore, RSVP and NHRP do not accommodatesimultaneous, point-to-multipoint (i.e., multicast) transmissions. Also,RSVP has limited scalability due to extension state information andconstant refreshment, and many conventional end-systems are not RSVPcapable.

The present invention overcomes the problems associated with the priorart, as described below.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is further described in the detailed descriptionthat follows, by reference to the noted drawings by way of non-limitingexamples of embodiments of the present invention, in which likereference numerals represent similar parts throughout several views ofthe drawings, and in which:

FIG. 1 is a diagram showing an exemplary network infrastructure,according to an aspect of the present invention;

FIG. 2 is a flow diagram illustrating an RSVP PATH procedure of anoriginating end-system, according to an aspect of the present invention;

FIG. 3 is a flow diagram illustrating an RSVP RESV procedure of adestination end-system corresponding to the RSVP path procedure of FIG.2, according to an aspect of the present invention;

FIG. 4 is a diagram showing an exemplary network infrastructure,including a proxy server for a non-RSVP capable destination end-system,according to an aspect of the present invention;

FIG. 5 is a flow diagram illustrating an RSVP PATH procedure of anon-RSVP capable destination end-system, according to an aspect of thepresent invention; and

FIG. 6 is a flow diagram illustrating an RSVP RESV procedurecorresponding to the RSVP PATH procedure of FIG. 5, according to analternative embodiment of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS

The present invention relates to enhancing RSVP to efficiently establishdynamic short-cut IP connections through an associated switched network.The enhancements include adding an extension object to the RSVPmessaging that identifies a switched network address of an originatinginterworking function device located in the IP network and the switchednetwork, without accessing a mapping database, server or the like. Thesystem is very scalable with a large number of subscribers and incursminimum administrative and operational overhead.

In view of the above, the present invention through one or more of itsvarious aspects and/or embodiments is presented to accomplish one ormore objectives and advantages, such as those noted below.

An aspect of the present invention provides a method for establishing anInternet protocol (IP) connection through a switched transport network,between an originating host device and a destination host devicecommunicating through an IP network, where the destination host deviceis incapable of resource reservation protocol (RSVP) signaling. Aswitched transport network address of a destination bridging device isassociated with its IP address, without communicating with an addressserver, in response to an RSVP path message initiated by an RSVP capableproxy device associated with the destination host device. The RSVP pathmessage is directed to the originating host device through the IPnetwork. The IP connection is established, through the switchedtransport network and the destination bridging device, in response to asetup message directed to the switched transport network address of thedestination bridging device.

The RSVP path message may contain at least one quality of service (QoS)parameter, which is passed to the setup message, so that the IPconnection is established in accordance with the QoS parameter. Theswitched transport network may be an asynchronous transfer mode (ATM)network or a multi-protocol label switching (MPLS) network. When theswitched transport network is an ATM network, each IP connection is aswitched virtual circuit (SVC) connection. Also, the setup message maybe a user-to-network interface (UNI) protocol message.

Another aspect of the present invention provides a method forimplementing an IP connection, through a switched transport network,between an originating host device and a destination host device,connected through an IP network, the destination host device beingincapable of RSVP signaling. The method includes communicating a requestfor the IP connection to an RSVP capable proxy signaling deviceassociated with the destination host device, inserting a switchedtransport network address of a destination bridging device into a firstdata field of an RSVP path message received from the proxy signalingdevice, and forwarding the path message to an originating bridgingdevice, through at least one router in the IP network by defaultrouting. The router passes the path message without modifying the firstdata field.

A setup message is forwarded to the destination bridging device, throughat least one switching device in the switched transport network, basedon the destination bridging device address retrieved from the first datafield. The setup message includes an RSVP reservation request messagegenerated in response to the path message. The IP connection isestablished between the originating host device and the proxy signalingdevice, through the originating bridging device and the destinationbridging device in response to the setup message. The proxy signalingdevice interfaces with the destination host device.

At least one QoS connection parameter may be included in a second datafield of the path message received from the proxy signaling device. Thesecond data field is included in the responsive reservation requestmessage. The IP connection is then established in accordance with theQoS service connection parameter, which may include a bandwidth.

The method for implementing the short-cut connection may further includecapturing the path message at the originating bridging device andstoring the address of the first bridging device from the RSVP extensionobject in association with an address of the destination host device,provided by the proxy signaling device. The stored address of thedestination bridging device is retrieved based on the address of thedestination host device included in the responsive reservation requestmessage. The setup message is then forwarded to the destination bridgingdevice based on the retrieved address.

Another aspect of the present invention provides a method and a systemfor providing a guaranteed QoS IP session, through an ATM network,between an originating end-system and a destination end-system that isincapable of RSVP signaling and therefore interfaces with an RSVPcapable proxy device. An initial IP session is established between theoriginating end-system and the destination end-system through an IPnetwork. An RSVP path message, including at least one parameter defininga QoS, is received from the proxy device, on behalf of the destinationend-system, at a destination interworking function (IWF) device.

An ATM address of the destination IWF device is inserted into atransport network hop (THOP) extension object of the path message. Thepath message is forwarded through the IP network by default routing toan originating IWF device without modifying the THOP extension object.The THOP extension object is then cached in association with an IPaddress of the destination end-system and a setup message is launchedthrough the ATM network based on the associated THOP extension objectand the IP address of the destination end-system. The setup messageincludes a responsive RSVP reservation request message, containing theQoS parameter. The setup message is received at the destination IWFdevice and an SVC connection is established between the destination IWFdevice and the originating IWF device in accordance with the QoSparameter. The reservation request message is forwarded to the proxysignaling device, which accepts the reservation request message onbehalf of the destination end-system. The initial IP session is thenshifted to the SVC connection.

Another aspect of the present invention provides a system forestablishing an IP connection between an originating host device and adestination host device through a switched transport network, where thedestination host device is incapable of RSVP signaling. The systemincludes an RSVP capable proxy device that interfaces with thedestination host device to provide RSVP signaling and an originatingbridging device that associates a switched transport network address andan IP address of a destination bridging device, without communicatingwith an address server, in response to an RSVP path message.

The RSVP path message is initiated by the proxy device and received bythe originating host device through an IP network, and the originatingbridging device responds with a setup message directed through theswitched transport network to the switched transport network address ofthe destination bridging device. The IP connection is established,through the switched transport network and the proxy device, in responseto the setup message. The setup message may include at least onepredetermined bidirectional flow parameter received from the pathmessage, so that the IP connection is established in accordance with thebidirectional flow parameter.

Another aspect of the present invention provides a system forestablishing an IP connection between an originating end-system and adestination end-system, which is incapable of RSVP signaling. The systemincludes a proxy signaling device, which interfaces with the destinationend-system, and a first IWF device, which inserts its switched transportnetwork address into a first data field of an RSVP path message receivedfrom the proxy signaling device. The path message is forwarded throughan IP network by default routing, which passes the path message withoutmodifying the first data field. A second IWF device receives the pathmessage and forwards a setup message to the first IWF device through theswitched transport network, based on the first IWF device's addressretrieved from the first data field of the path message. The setupmessage includes an RSVP reservation request message generated inresponse to the path message. The IP connection is established betweenthe originating end-system and the destination end-system, through thefirst bridging device, the second bridging device and the proxysignaling device, in response to the setup message.

Yet another aspect of the present invention provides computer datasignaling, embodied on a propagation medium, that enables an IPconnection across a switched transport network between an originatinghost device and a destination host device, through a first bridgingdevice and a second bridging device, where the destination host deviceis incapable of RSVP signaling. The computer data signaling includesfirst and second path message signals, a reservation request messagesignal and first and second setup message signals. The first pathmessage signal is received from a proxy signaling device connected tothe destination host device, and includes an address parameter for thesecond bridging device and an IP address of the proxy signaling device.The second path message signal is forwarded through an IP networkwithout modification to the address parameter, and includes a switchedtransport network address of the second bridging device in the addressparameter and the IP address of the proxy signaling device. Thereservation request message signal is received by the first bridgingdevice in response to the second path message, and includes the IPaddress of the proxy signaling device.

The first setup message signal is forwarded through the switchedtransport network to the transport network address of the secondbridging device, retrieved from the second path message signal. Thefirst setup message signal includes the reservation request messagesignal. The second setup message signal is forwarded to the IP addressof the proxy signaling device, and includes the reservation requestmessage signal. The IP connection is established in response to thesecond setup message signal.

The path message signals and the reservation request message signal mayinclude a bidirectional flow parameter that defines at least onepredetermined QoS attribute of the IP connection. The IP connection isthen established in accordance with the QoS attribute, which may includea bandwidth. The path message signals and the reservation requestmessage signal may further include a reverse charging parameter.Accounting data for the IP connection is associated with the originatinghost device when the reverse charging parameter is activated and withthe destination host device when the reverse charging parameter is notactivated. The path message signals and the reservation request messagesignal may comply with RSVP, and the setup message signals may complyUNI protocol.

The various aspects and embodiments of the present invention aredescribed in detail below.

FIG. 1 is a diagram depicting an exemplary network infrastructuresupporting the present invention. As stated above, the enhancements toRSVP enable short-cut IP connections to be established over switchednetworks. FIG. 1, in particular, depicts an exemplary ATM network 8through which the short-cut IP connection may be established, operatingin conjunction with the IP network 6. The present invention is notlimited to ATM networks. The invention may be implemented over any RSVPcapable switched network that interfaces with the IP network 6,including, for example, a multi-protocol label switching (MPLS) network.For example, in alternative embodiments, the switching network includesMPLS routers, optical switching devices controlled by generalized MPLS(GMPLS), or time division multiplex (TDM) switching devices controlledby GMPLS. The associated connection setup requests would be inaccordance with RSVP-te or constraint-based routed label distributionprotocol (CR-LDP).

The ATM network 8 includes ATM edge switch 22 and ATM edge switch 24.Although not pictured, the ATM network 8 may further include multipleATM core switches situated between the edge switches without affectingimplementation of the present invention. The IP network 6 is depicted toinclude IP router 14 and IP router 16. The IP network 6 may likewiseinclude any number of intervening IP routers to enable best effortrouting of IP traffic. The ATM network 8 and the IP network 6 sharebridging devices to interface between the networks. In particular, bothnetworks include an interworking function (IWF) device 12, through whichthe originating end-system 10 accesses the networks, and an IWF device18, through which the destination end-system 20 accesses the networks.The IWF devices 10 and 18 may be multiple devices or any combination ofhardware and software that translate between RSVP of the IP network 6and user-to-network interface (UNI), or other signaling, of the ATMnetwork 8. For example, the IWF device 12 may be a digital subscriberline (DSL) modem and the IWF device 18 may be an SVC router. The ATMnetwork 8 uses a signaling protocol to allocate network resources and toestablish SVCs, which are dynamically set up and removed according toneed (as opposed to permanently configured PVCs).

Each of the IWF devices 12 and 18 include two physical ports. One portinterfaces with the local area network (LAN), through which theyrespectively communicate with the originating IP end-system 10 and thedestination IP end-system 20. The other physical port interfaces with awide area network (WAN), such as the ATM network 8. The WAN portincludes multiple logical ports, depending on the number of sessions tobe established through the WAN.

In an embodiment of the invention, the originating end-system 10 and thedestination end-system 20 are RSVP capable IP devices. The end-systemsmay include, for example, individual personal computers or workstations,enterprise networks, ISPs and peer networks. A typical implementation isthe originating end-system 10 being an Internet service subscriber andthe destination end-system 20 being an ISP. The originating end-system10 maintains its own IP address, domain naming system (DNS) and other IPconfigurations. The DNS translates the name of the originatingend-system 10 into an IP address or a universal resource locator (URL).

In an alternative embodiment, an example of which is shown in FIG. 4,one or both end-systems are not RSVP capable, in which case a proxy mustbe incorporated to enable the RSVP communications. A proxy is a device,other than an end-system, that provides appropriate signaling on behalfof the end-systems for communications to be established. An advantage ofusing a proxy is that the invention may be implemented in existingnetworks without modifying every IP device to accommodate RSVPsignaling. For example, when the destination end-system 20 is not RSVPcapable, it connects to a proxy server 30, as shown in FIG. 4. The proxyserver 30 then initiates the RSVP messaging to enable the short-cut IPconnection over the ATM network 8, or other transport networks, asdescribed in detail below.

As stated above, the originating end-system 10 that desires a short-cutIP connection through the ATM network 8 conventionally establishes an IPsession with the destination end-system 20, using best effort routingbased on TCP/IP and UDP/IP, for example, and the IP addresses of the twoend-systems. The short-cut will be set up using RSVP, which reserves acommunications route between the end-systems based on RSVP messagespassed through the IP network 6 and ultimately the ATM network 8. Thebasic RSVP message types include path (PATH) messages, reservationrequest (RESV) messages, path tear down (PATHTEAR) messages, reservationtear down (RESVTEAR) messages and reservation confirmation (RESVCONF)messages.

Generally, the conventional PATH messages defines the communication pathby traveling downstream through the IP network from the originatingend-system 10 to the destination end system 20, following the same besteffort route as the data packets in the IP session. Typically, a PATHmessage causes each router to store the IP address of the previousrouter to enable a corresponding RESV message to travel upstream alongthe same route, in the reverse direction.

The PATH message reaches the destination end-system 20, which generatesand sends the corresponding RESV message. Each router sequentiallyreceives the RESV message, which includes information regarding thefunctionality of the previous router, and accepts or rejects thereservation. When a reservation is accepted, the router sends an RESVmessage to the next router on the path. When the RESV message reachesthe originating end-system, the reservation is established through theIP network between the two end-systems. When the end-system 20, whichinitiates the RESV message, requests confirmation through the RESVmessage, an RESVCONF message is returned to confirm the reservation. Theend-systems may terminate the path by sending a PATHTEAR message, whichflows in the same direction as the PATH message, or an RESVTEAR message,which flows in the same direction as the RESV message.

The RSVP messages include various objects defining parameters of therequested connection. Examples of conventional RSVP objects include theFLOWSPEC object, the SENDER_TEMPLATE object and the SESSION object. TheFLOWSPEC object describes the specifications of the traffic stream sentfrom the originating end-system 10, including the required QoS of thedesired connection, and the service requirements of the application. TheSENDER_TEMPLATE object provides the source IP address and the sourceport number, which correspond to the originating end-system 10. TheSESSION object provides the destination IP address and the destinationport number, which correspond to the destination end-system 20.

Conventionally, the switched network includes a server, e.g., an ARPserver, accessible by the IWF devices 12 and 18 to associate the IPaddresses of the end-systems 10 and 20 and the IWF devices 12 and 18with the respective switched network (e.g., ATM network) addresses,enabling translation of the IP address to the ATM address. For example,an ARP server may perform the IP to ATM address translation forend-systems and routers within a local IP subnet (LIS). The presentinvention eliminates the need for the server based on enhancements toRSVP.

In particular, an RSVP extension that defines a transport network hop(THOP) is included in the RSVP messaging. THOP may include up to threeadditional classes of objects: RSVP_THOP, RSVP_CYSPEC and RSVP_SVCSPEC.In an embodiment of the invention, the RSVP_THOP class includes threeobjects, each of which may only be included in the RSVP PATH message asit traverses the IP network between the originating end-system 10 andthe destination end-system 20. The objects follow the format described,for example, in Request for Comment (RFC) 2205, “Resource ReservationProtocol (RSVP)—Version 1 Functional Specification,” the disclosure ofwhich is expressly incorporated by reference herein in its entirety. Theclass number should be at least 192 (e.g., 11bbbbbb, where 1 is amandatory bit and b is optional) to assure proper routing.

Each of the objects represent the address of the previous hop located ina switched network, e.g., the ATM network 8 or an MPLS network. Thefirst two objects of the RSVP_THOP class represent addresses in an MPLSnetwork. For example, the first object is the IPv4 RSVP_THOP object,which represents the IP address of the previous hop in an MPLS networkusing the IPv4 protocol. The object contains 4 octets to accommodate the32 bit address field associated with conventional IP addresses. Thesecond object is the IPv6 RSVP_THOP object, which represents the IPaddress of the previous hop in an MPLS network using the IPv6 protocol.The object contains 16 octets to accommodate the expanded 128 bitaddress field. The IPv6 protocol enables additional features of the MPLSnetwork, including enhanced security and multicasting, for example. Thethird object is the ATM RSVP_THOP object, which represents the addressof the previous hop located in the ATM network 8. The object may contain20 octets to accommodate network service access point (NSAP) addressing.

Each of the objects in the RSVP_THOP class essentially function in thesame manner with respect to representing transport network addresses ofMPLS or ATM switching devices, according to the alternative embodimentsof invention. Therefore, the implementation of the ATM RSVP_THOP objectin an ATM network, as described below, is equally applicable to the IPv4and IPv6 RSVP_THOP objects in an MPLS network.

The ATM RSVP_THOP object carries the ATM transport network address ofthe originating interface or bridging device, such as the IWF device 12,through which the PATH message was most recently sent. Only nodes orrouters that interface with both the initial transport network (e.g.,the IP network 6) and a different, switched transport network (e.g., theATM network 8) respond to the ATM RSVP_THOP object. For example, the IWFdevice 12 inserts its ATM address into the ATM RSVP_THOP object and theIWF device 18 retrieves the address, while all other IP devices, such asthe IP network routers 14 and 16, pass the ATM RSVP_THOP object withoutmodification. Multiple ATM RSVP_THOP objects may be included in the samePATH message to accommodate interim IWF devices. The order of themultiple objects is last-in-first-out (LIFO).

The RSVP_CYSPEC class has a class number different from the RSVP_THOPclass and includes one object, for example, which may be included in theRSVP PATH and RESV messages. The object is the RSVP_CYSPEC object, whichrepresents bidirectional flow specifications. The object includes aTSPEC field and an RSPEC field, each of which includes RSVP FLOWSPECdata without the header, e.g., as described in RFC 2210, “The Use ofRSVP with IETF Integrated Services,” the disclosure of which isexpressly incorporated by reference herein in its entirety. The TSPECfield describes the sending flow specifications (e.g., the ingress QoS)and the RSPEC field describes the receiving flow specifications (e.g.,the egress QoS). Accordingly, the RSVP_CYSPEC object is able to describethe QoS which the short-cut IP connection must support.

The RSVP_SVCSPEC class has another class number, different from theRSVP_CYSPEC and RSVP_THOP classes, and includes one object, which may becontained in the RSVP PATH and RESV messages. The object is theRSVP_SVCSPEC object, which represents the service specifications andsupports value-added RSVP service signaling among the IP devices. Theobject includes a reverse charge indicator field to indicate whether theRSVP PATH message sender, e.g., the originating end-system 10, is to payfor the connection. The reverse billing enabled by the RSVP_SVCSPECobject is necessary because the switched network through which the IPshort-cut connection is established treats the RSVP PATH messagereceiver, e.g., the destination end-system 18, as the calling party eventhough the connection is initiated by the originating end-system 10. Thereverse billing enables accounting data to be associated with theoriginating end-system 10, which may then be billed for the connection,when appropriate.

Accordingly, the reverse charge indicator of the RSVP_SVCSPEC objectcontains a Boolean value. A value of 1 (TRUE) indicates that the calledparty, e.g., the originating end-system 10, is to be billed. A value of0 (FALSE) indicates the called party not be billed. In other words, thecalling party, e.g., the destination end-system 20, is billed or thecall is toll free. The destination IWF device 18 sets the reverse chargeindicator in the switched network call setup message when theRSVP_SVCSPEC object indicates a value of 1. When the switching networkUNI signaling does not support reverse charging, the interworking devicerejects the RSVP message and generates a corresponding error message.

FIGS. 2 and 3 are flow diagrams illustrating an exemplary RSVP-basedguaranteed QoS IP connection over the ATM network 8. FIG. 2 depicts anRSVP path procedure initiated by the originating end-system 10. Inparticular, the originating end-system 10, or the initiating host,desiring the IP short-cut connection through the ATM network 8conventionally establishes a default IP connection with the destinationend-system 20 using best effort routing, e.g., TCP/IP or UDP/IP, and theIP addresses of the two end-systems. An RSVP session may be initiatedusing RSVP with minor extension. When the originating end-system 10requests a short-cut connection over the ATM network 8, e.g., as aresult of specific QoS session requirements, the connection may bedynamically established between the bridging devices, IWF device 12 andIWF device 18, each of which is capable of translating between RSVP andUNI protocol signaling. The general connection setup protocol betweenthe IWF devices and the ATM network 8 may be UNI signaling withconfirmation procedure, such as ATM UNI Specification—version 3.1 orversion 4.0.

To establish the short-cut IP connection, the originating end-system 10generates and sends an RSVP PATH message to the IWF device 12 at step220 of FIG. 2. The connection between the originating end-system 10 andthe IWF device 12 is established through regular IP connectivity, suchas IP over Ethernet. According to the invention, the PATH messageincludes the QoS specifications for the desired connection, such as thebidirectional QoS specification object RSVP_CYSPEC, which describes theingress QoS and the egress QoS. The RSVP_CYSPEC object is associatedwith, and may replace, standard routing RSVP objects, such as the RSVPSENDER_TEMPLATE object, which provides the IP address and the portnumber of the originating end-system 10, and the RSVP SESSION object,which provides the IP address and the port number of the destinationend-system 20.

At step 222, the originating IWF device 12 captures the PATH message andinserts its ATM address, e.g., the ATM network service access point(NSAP) address, into the PATH message as the ATM RSVP-THOP object,discussed above. The IWF device 12 also caches the PATH message forcomparison to the returned RESV message, discussed below. The PATHmessage travels downstream from the IWF device 12 to the destination IWFdevice 18, following the same route as the regular data packets. Inparticular, the IWF device 12 forwards the PATH message, including theATM RSVP_THOP object, to the IP router 14 at step 224, which routes thePATH message to the IP router 16 at step 226. The IP router 16 thenroutes the PATH message to the destination IWF device 18 at step 228.Significantly, even though the default connection routers, e.g., the IProuter 14 and the IP router 16, typically modify the previous hopaddress passed in the PATH message, they do not modify the ATM RSVP_THOPobject.

In the depicted embodiment of the invention, the IP transport network 6carrying the default connection is separate from the ATM network 8,which includes the ATM edge switches 22 and 24. However, alternativeembodiments include the default IP connection being carried by the sameATM network through which the short-cut is ultimately established.

At step 230, the IWF device 18 captures the PATH message and caches themapping of the IP address of the originating end-system 10 to theaddress in the ATM RSVP_THOP object and forwards the PATH message to thedestination end-system 20. The destination end-system 20 receives andvalidates the PATH message. In an embodiment of the invention, the IWFdevice 18 removes the ATM RSVP_THOP object before passing the PATHmessage to the destination end-system 20. Removing the object avoids thepossibility of the destination end-system 20 not recognizing the ATMRSVP_THOP object and rejecting the connection.

FIG. 3 is a flow diagram depicting the RSVP reserve messaging (RESV)sent through the ATM network 8 in response to the received RSVP PATHmessage. The destination end-system 20 generates and sends an RSVP RESVmessage to the IWF device 18 at step 340. Like the PATH message, theRESV message may contain an RSVP_CYSPEC extension object, confirmingbidirectional traffic characteristics of the QoS IP flow, instead of theRSVP_FLOWSPEC object. When the RESV message does not contain theRSVP_CYSPEC object, the upstream traffic characteristics of thebidirectional shortcut are handled according to local protocol. In anembodiment of the invention, the upstream QoS may be algorithmicallycalculated from the RSVP_FLOWSPEC object. The RESV message may furthercontain the RSVP_SVCSPEC object to enable reverse billing, whennecessary.

The IWF device 18 initially captures the RESV message at step 342. Toestablish an ATM SVC at the requested QoS through broadband accesslines, such as DSL, Ethernet or TDM, the IWF device 18 launches a callsetup message, e.g., an ATM UNI signaling protocol SETUP message, to thelongest short-cut bridging device address indicated by the previouslycached ATM RSVP_THOP object. In the present example, the longestshort-cut bridging device address is the ATM address of the IWF device12. In other words, had the PATH message passed through intermediate IWFdevices, which had respectively inserted additional ATM RSVP_THOPobjects, the SETUP message would be directed to the address contained inthe first inserted ATM RSVP_THOP object, i.e., the originating IWFdevice 12. The UNI signaling enables the transfer of information acrossthe ATM network 8. For example, the user-to-user information element (UUIE) of the UNI SETUP message may contain the RSVP RESV message to besent across the ATM network 8 to the IWF device 12. The assignment ofthe RESV message in UU IE follows routing protocol criteria RFC 3033,“The Assignment of the Information Field and Protocol Identifier in theQ.2941 Generic Identifier and the Q.2957 User-to-User Signaling for theInternet Protocol,” the disclosure of which is expressly incorporated byreference herein in its entirety.

The IWF device 18 initially sends the SETUP message, along with the RESVmessage, to the ATM edge switch 24 at step 344. The ATM edge switch 24confirms receipt of the SETUP message and forwards the message to theATM edge switch 22 at step 348. The message may also pass throughintervening ATM core switches in the ATM network 8 (not pictured), usingprivate network-to-network interface (PNNI) signaling protocol, forexample. The ATM edge switch 22 forwards the SETUP message to the IWFdevice 12 at step 350.

The IWF device 12 validates the UNI SETUP and the RESV messages with thecached PATH message at step 351. Also, to confirm the connection acrossthe ATM network 8, the IWF device 12 sends a CONN message to the ATMedge switch 22 at step 352, which acknowledges the confirmation signalby returning a CONN ACK message to the IWF device 12 at step 354.Likewise, the ATM edge switch 22 sends a CONN message to the ATM edgeswitch 24 at step 356, which returns a CONN ACK message at step 358. TheATM edge switch 24 sends a CONN message to the IWF device 18 at step360, which returns a CONN ACK message at step 362, completing theconnection confirmation cycle.

Meanwhile, after the originating IWF device 12 validates the UNI SETUPmessage and the RSVP RESV message, an ATM SVC at the requested QoS issetup between the originating IWF device 12 and the destination IWFdevice 18 through broadband access lines, as indicated by step 364. TheSVC provides a short-cut between the IWF devices by bypassing the IPnetwork 6. The IWF device 18 accordingly creates an entry in itsforwarding table indicating the successful setup of the ATM SVC, anexample of which is shown in Table 1.

TABLE 1 Forward to Destination IP Source IP Port Interface Any localor * * LAN private address originating end- destination TCP/UDP WAN—newQoS system 10 end-system 20 port SVC * * * WAN—default ATM connection

The first three columns of Table 1 indicate the incoming interface ofthe IWF device 18 and the last column indicates the outgoing interfaceof the IWF device 18. Therefore, as indicated by the first row of Table1, when the destination IP data received at the IWF device 18 indicatesany local or private IP address, the IWF device 18 directs theassociated connection through the LAN interface. The asterisks in thefirst row indicate that the source IP address and the port informationdoes not affect the forward to interface when the destination IP dataindicates a local or private IP address.

As indicated by the second row of Table 1, when data is received at theTCP/UDP port and provides that the destination IP address is theoriginating end-system 10 and the source IP address is the destinationend-system 20, the output of the IWF device 18 directs the connectionover the new short-cut SVC through the WAN interface, identified by anassociated virtual path indicator (VPI) and virtual channel indicator(VCI). As indicated by the asterisks in the third row of Table 1,incoming data directed to a port other than the TCP/UDP port, orindicating destination and source IP addresses other than theoriginating end-system 10 and the destination end-system 20,respectively, invoke the default ATM connection of the WAN interface.

Similarly, the IWF device 12 creates an entry in its forwarding tableindicating the successful setup of the ATM SVC, an example of which isshown in Table 2.

TABLE 2 Forward to Destination IP Source IP Port Interface Any localor * * LAN private address destination end- originating TCP/UDP WAN—newQoS system 10 end-system 20 port SVC * * * WAN—default ATM connection

The IWF device 12 also forwards the RESV message to the originatingend-system 10 at step 370. When the originating end-system 10 acceptsthe RESV message, a short-cut IP connection at the requested QoS isavailable over the newly established SVC between the IWF device 12 andthe IWF device 18, enabling communication between the originatingend-system 10 and the destination end-system 20, indicated at step 372.The short-cut IP connection is based on RFC 1483, “MultiprotocolEncapsulation Over ATM Adaptation Layer 5,” the disclosure of which isexpressly incorporated by reference herein in its entirety. After theshort-cut is established and available at step 372, the QoS IP sessionis moved from the IP network 6 to the new SVC based QoS short-cut in theATM network. In other words, the IP traffic travels the dedicated QoSshort-cut path between the originating end-system 10 and the destinationend-system 20 through the ATM switches 22 and 24, as opposed to thehop-by-hop default IP path through the IP routers 14 and 16.

Typically, the SVC is torn down through ATM UNI signaling. Furthermore,the soft state natural of the RSVP 2205 protocol is maintained at the IPdevices, including the IWF devices 12 and 18, to avoid an orphaned QoSshort-cut when the IP session is disconnected by default. Substantiallosses of RSVP refreshment messages will cause the QoS short-cut toautomatically tear-down through the UNI signaling. Also, either theoriginating end-system 10 or the destination end-system 20 may cause theSVC to be torn down by sending an RSVP PATHTEAR or RESVTEAR message,respectively. The IWF devices 12 and 18 respond by tearing down the ATMSVC, along with the RSVP session.

The traffic characteristics of the QoS short-cut are constructed fromRSVP traffic characteristics objects according to RFC 2210, “The Use ofRSVP with IETF Integrated Services;” RFC 2211, “Specification of theControlled-Load Network Element Service;” and RFC 2212, “Specificationof Guaranteed Quality of Service,” the disclosures of which areexpressly incorporated by reference herein in their entireties. For ATMSVC networks in particular, the traffic characteristics are constructedfrom RSVP traffic characteristics objects according to RFC 2381,“Inter-operation of Controlled-Load Service and Guaranteed Service withATM,” and RFC 2382, “A Framework for Integrated Service and RSVP overATM,” the disclosures of which are expressly incorporated by referenceherein in their entireties.

The present invention further enables multiple simultaneous IP short-cutconnections among multiple endpoints. Each IP connection is apoint-to-point connection with a unique set of connection parameters,including a source address, source port number, destination address anddestination port number, suitable for IP virtual private network (VPN)service with specific QoS requirements. At least one of the fourparameters must be different in order to enable a simultaneous IPshort-cut connection. For example, different addresses for thedestination end-systems, as well as different port assignment for eachconnection, enable the simultaneous IP short-cut connections from theoriginating end-system 10.

Setting up each of the additional simultaneous connections involvesessentially the same processing steps described above. Generally, theoriginating IWF device 12 captures the PATH message from the originatingend-system 10, including the ATM RSVP_THOP object, and inserts its ATMaddress as the ATM RSVP_THOP object. The IP routers forward the PATHmessage to an appropriate destination IWF device (which may be differentfrom the destination IWF device 18) without altering the ATM RSVP_THOP.The destination IWF device forwards the PATH message to a seconddestination end-system, which receives and validates the PATH message.

The second destination end-system then generates and sends acorresponding RSVP RESV message. A UNI SETUP message, containing theRSVP RESV message, is routed by the destination IWF device through theATM network 8 to the originating IWF device 12 based on the ATM addresspreviously inserted as the ATM RSVP_THOP object. A second ATM SVCconnection is established between the originating IWF device 12 and thedestination IWF device at the requested QoS. As stated above, to enablethe second ATM SVC connection, there must be at least one connectionparameter (e.g., the source address, the source port number, thedestination address and/or the destination parameter) that is differentfrom the corresponding connection parameter associated with the firstATM SVC connection. The originating IWF device 12 forwards the RSVP RESVmessage to the originating end-system 10 to complete the ATM SVC betweenthe originating end-system 10 and the second destination end-system.

The present invention also enables the originating end-system 10 to betemporarily assigned alternate IP addresses, associated with aparticular destination address. For example, when the originatingend-system 10 has a public IP address, and the user wishes to access aprivate or secure network, the destination end-system within the desirednetwork must generate an alternate IP address to enable the session. Forgenerating a temporary IP address, the process is essentially the sameas described above with respect to FIGS. 2 and 3, with the addition of adynamic host configuration protocol (DHCP) extension object in the RSVPmessaging. The DHCP extension object enables a TCP/IP host, e.g., theoriginating end-system 10, to receive temporary (as well as permanent)IP addresses from centrally administered servers, for example, at thedirection of the destination end-system 20.

Accordingly, the originating end-system 10 generates and sends RSVP PATHmessages corresponding to the desired IP connection with the destinationend-system 20 to the IWF device 12 at step 220 of FIG. 2 through regularIP connectivity. Each PATH message must include the DHCP extensionobject. Each PATH message may likewise contain the bidirectional QoSspecification object RSVP_CYSPEC, which describes the ingress QoS andthe egress QoS for the IP connection.

The originating IWF device 12 captures the PATH message at step 222 andinserts its ATM address into the PATH message as the ATM RSVP-THOPobject. The IWF device 12 caches the PATH message for comparison to thereturned RESV message. The PATH message, including the DHCP extensionobject and the ATM RSVP_THOP object, travels downstream from the IWFdevice 12 to the IP router 14 at step 224, the IP router 16 at step 226and the destination IWF device 18 at step 228. As described above, theIP router 14 and the IP router 16 do not modify the ATM RSVP_THOP objectupon receipt of the PATH message. At step 230, the IWF device 18captures the PATH message, caches the mapping of the IP address of theoriginating end-system 10 to the address in the ATM RSVP_THOP object andremoves the ATM RSVP_THOP object.

At step 232, the IWF device 18 passes the PATH message to thedestination end-system 20, which receives and validates the PATHmessage. The destination end-system 20 responds by generating an RSVPRESV message with a DHCP extension object (i.e., DHCP response), whichincludes a newly assigned IP address associated with the originatingend-system 10.

Referring again to FIG. 3, the destination end-system 20 sends the RSVPRESV message to the IWF device 18 at step 340. Like the PATH message,the RESV message may contain an RSVP_CYSPEC extension object, confirmingbidirectional traffic characteristics of the QoS IP flow. The RESV mayfurther contain the RSVP_SVCSPEC object to enable reverse billing, asdiscussed above. The IWF device 18 captures the RESV message at step 342and establishes an ATM SVC at the requested QoS through broadband accesslines. In particular, the IWF device 18 launches the ATM UNI signalingprotocol SETUP message to the address of the previously cached ATMRSVP_THOP object, which is the ATM address of the IWF device 12. The UNISETUP message contains the RSVP RESV message, including the DHCPresponse, which is sent across the ATM network 8 to the IWF device 12.

The IWF device 18 initially sends the SETUP message, along with the RESVmessage, to the ATM edge switch 24 at step 344. The ATM edge switch 24confirms receipt of the SETUP message and forwards the message (throughany intervening ATM core switches) to the ATM edge switch 22 at step348. The ATM edge switch 22 forwards the SETUP message to theoriginating IWF device 12 at step 350. The IWF device 12 validates theUNI SETUP and the RESV message with the cached PATH message at step 351.Also, to confirm the IP connection across the ATM network 8, the IWFdevice 12 sends a CONN message to the ATM edge switch 22 at step 352,which acknowledges the confirmation signal by returning a CONN ACKmessage to the IWF device 12 at step 354. Likewise, the ATM edge switch22 sends a CONN message to the ATM edge switch 24 at step 356, whichreturns a CONN ACK message at step 358. The ATM edge switch 24 sends aCONN message to the IWF device 18 at step 360, which returns a CONN ACKmessage at step 362, completing the connection confirmation cycle.

Meanwhile, after the originating IWF device 12 validates the UNI SETUPmessage and the RSVP RESV message, an ATM SVC at the requested QoS isset up between the originating IWF device 12 and the destination IWFdevice 18 for one of the multiple connections, as indicated at step 364.The IWF device 18 then creates an entry in its forwarding tableindicating the successful setup of the ATM SVC, including the IP addressassigned by the destination end-system 20 to the originating end-system10, an example of which is shown in Table 3.

TABLE 3 Forward to Destination IP Source IP Port Interface Any localor * * LAN private address new IP address * * WAN—new QoS assigned tothe SVC originating end- system 10 * * * WAN—default ATM connection

The first three columns of Table 3 indicate the incoming interface ofthe IWF device 18 and the last column indicates the outgoing interfaceof the IWF device 18. Therefore, as indicated by the first row of Table3, when the destination IP data received at the IWF device 18 indicatesa local or private IP address, the IWF device 18 directs the associatedconnection through the LAN interface, as discussed above with respect toTable 1. As indicated by the second row of Table 3, when data receivedon any port indicates that the destination IP address is the newlyassigned IP address of the originating end-system 10, the output of theIWF device 18 directs the connection over the new short-cut SVC throughthe WAN interface, identified by an associated VPI and VCI. As indicatedby the asterisks across the third row of Table 3, incoming dataindicating any other destination IP address or source IP address invokesthe default ATM connection of the WAN interface.

The IWF device 12 similarly creates an entry in its forwarding tableindicating the successful setup of the ATM SVC, also including the IPaddress assigned by the destination end-system 20 to the originatingend-system 10, an example of which is shown in Table 4.

TABLE 4 Forward to Destination IP Source IP Port Interface Any localor * * LAN private address * new IP address * WAN—new QoS assigned tothe SVC originating end- system 10 * * * WAN—default ATM connection

The IWF device 12 also forwards the RESV message to the originatingend-system 10 at step 370. The originating end-system 10 obtains thenewly assigned IP address from the DHCP response contained in the RSVPmessage, as well as other IP configuration information, such as DNS. Theoriginating end-system 10 then installs the new IP interface based onthe IP configuration information. An RFC 1483 based IP connectionbetween the originating end-system 10 and the destination end-system 20at the requested QoS is available over the newly established SVC betweenthe IWF device 12 and the IWF device 18, indicated by step 372. Afterthe short-cut is established and available at step 372, the QoS IPsession is moved from the IP network 6 to the new SVC based QoSshort-cut in the ATM network. In other words, the IP traffic thentravels the short-cut path between the originating end-system 10 and thedestination end-system 20 through the ATM switches 22 and 24, as opposedto the hop-by-hop default IP path through the IP routers 14 and 16.

Notably, the originating end-system 10 may initiate additional,simultaneous IP connections to other destinations following the samesteps discussed above with respect to FIG. 2. Because the additional IPconnections may not include the destination end-system 20, the IP router16, the IWF device 18 and the ATM edge switch 24 may not be involved.However, similar devices will be used to route and process the RSVP andUNI messages to establish the simultaneous, multiple IP short-cutconnections across the ATM network 8. Each of the QoS short-cutconnections may treat the originating end-system 10 as having a uniqueIP address, generated in response to the DHCP extension object.

Setting up each of the additional simultaneous connections involves thesame processing steps described above. Generally, the originating IWFdevice 12 captures the PATH message from the originating end-system 10,including the ATM RSVP_THOP object and the DHCP extension object, andinserts its ATM address as the ATM RSVP_THOP object. The IP routersforward the PATH message to an appropriate destination IWF devicewithout altering the ATM RSVP_THOP. The destination IWF device forwardsthe PATH message to a second destination end-system, which receives andvalidates the PATH message.

The second destination end-system then generates and sends acorresponding RSVP RESV message, including a DHCP response with anothernewly assigned IP address associated with the originating end-system 10.A UNI SETUP message, containing the RSVP RESV message, is routed by thesecond destination IWF device through the ATM network 8 to theoriginating IWF device 12 based on the ATM address previously insertedas the ATM RSVP_THOP object. A second ATM SVC connection is establishedbetween the originating IWF device 12 and the second destination IWFdevice at the requested QoS. The originating IWF device 12 forwards theRSVP RESV message to the originating end-system 10, which obtains thenewly assigned IP address from the DHCP response from the RSVP message,to complete the ATM SVC between the originating end-system 10 and thesecond destination end-system using the second newly assigned IPaddress.

As discussed above, an alternative embodiment of the invention includesthe use of proxy devices to accommodate IP devices having no RSVPcapability. For example, FIG. 4 is a diagram depicting an exemplarynetwork infrastructure that includes a proxy server 30 and a contentserver 32 associated with the destination end-system 20, which is notRSVP capable. The proxy server 30 is RSVP capable and generates theappropriate RSVP signaling on behalf of the destination end-system 20based on flow information obtained from the content server 32. The flowinformation includes, for example, the source IP address, thedestination IP address, the port identifier, the ingress QoS and theegress QoS.

FIG. 5 is a flow diagram illustrating an RSVP PATH procedure involvingthe non-RSVP capable destination end-system 20. As described withrespect to the RSVP capable destination end-system 20, the originatingend-system 10 desiring the short-cut IP connection first conventionallyestablishes a default IP connection with the destination end-system 20at step 520 using the default routing, e.g., best effort routing, andthe IP addresses of the two end-systems. However, the originatingend-system 10 does not initiate the RSVP PATH message. Rather, thedestination end-system 20 communicates the QoS IP session request to theproxy server 30 at step 522 through the content server 32. The proxyserver 30 obtains the flow information from the content server 32 atsteps 524 and 526.

To establish the short-cut IP connection, the proxy server 30 generatesand sends an RSVP PATH message to the IWF device 18 at step 528. Theconnection between the proxy server 30 and the IWF device 18 isestablished through regular IP connectivity. The PATH message includesthe RSVP extension objects discussed above, such as the reverse chargingobject RSVP_SVCSPEC and the bidirectional QoS specification extensionobject RSVP_CYSPEC. The RSVP_CYSPEC object is associated with, and mayreplace, standard routing RSVP objects, such as the RSVP SENDER_TEMPLATEobject, which provides the IP address and the port number of thedestination end-system 20, and the RSVP SESSION object, which providesthe IP address and the port number of the originating end-system 10. TheRSVP_SVCSPEC object indicates to the network carrier that thedestination end-system 20 will take the usage charge of the ATM SVC.

At step 530, the originating IWF device 18 captures the PATH message andinserts its ATM address into the PATH message as the ATM RSVP-THOPobject. The IWF device 18 also caches the PATH message for comparison tothe returned RESV message, discussed below. The PATH message travelsfrom the IWF device 18 to the destination IWF device 12, following thesame route as the regular data packets. In particular, the IWF device 18forwards the PATH message, including the ATM RSVP_THOP object, to the IProuter 16 at step 532, which routes the PATH message to the IP router 14at step 534. The IP router 14 then routes the PATH message to theoriginating IWF device 12 at step 536. As discussed above, the IP router14 and the IP router 16 do not modify the ATM RSVP_THOP object uponreceipt of the PATH message. At step 538, the IWF device 12 captures thePATH message and caches the mapping of the IP address of the destinationend-system 20 (i.e., the content server 32) to the address in the ATMRSVP_THOP object.

Because this is a reverse charging PATH request involving the proxyserver 30, the IWF device 12 generates and sends an RSVP RESV message atstep 640 of FIG. 6, without forwarding the PATH message to theoriginating end-system 10. Like the PATH message, the RESV message maycontain the RSVP_CYSPEC object and the RSVP_SVCSPEC object. Inparticular, in order to establish the ATM SVC, the IWF device 12launches an UNI SETUP message to the longest short-cut bridging deviceaddress indicated by the previously cached ATM RSVP_THOP object, whichis the ATM address of the IWF device 18 in the present example. The UUIE of the UNI SETUP message contains the RSVP RESV message to be sentacross the ATM network 8 to the IWF device 18.

The IWF device 18 sends the SETUP message, along with the RESV message,to the ATM edge switch 22 at step 640. The ATM edge switch 22 confirmsreceipt of the SETUP message and forwards the message to the ATM edgeswitch 24 at step 644. The message may also pass through intervening ATMcore switches in the ATM network 8 (not pictured). The ATM edge switch24 forwards the SETUP message to the IWF device 18 at step 646, whichvalidates the UNI SETUP and the RESV messages with the cached PATHmessage at step 648. Also, to confirm the connection across the ATMnetwork 8, the IWF device 18 and the ATM edge switches 22 and 24exchange CONN and CONN ACK messages (not pictured) to complete theconfirmation cycle, as discussed above with respect to FIG. 3.

After the IWF device 18 validates the UNI SETUP message and the RSVPRESV message, an ATM SVC at the requested QoS is set up between theoriginating IWF device 12 and the destination IWF device 18 throughbroadband access lines, as indicated by step 650. The IWF device 18accordingly creates an entry in its forwarding table indicating thesuccessful set up of the ATM SVC, an example of which is shown in Table5.

TABLE 5 Forward to Destination IP Source IP Port Interface Any localor * * LAN private address destination end- originating TCP/UDP WAN—newQoS system 20 end-system 10 port SVC * * * WAN—default ATM connection

As discussed above with respect to Table 1, the first three columns ofTable 5 indicate the incoming interface of the IWF device 18 and thelast column indicates the outgoing interface of the IWF device 18.Therefore, as indicated by the first row, when the destination IP datareceived at the IWF device 18 indicates any local or private IP address,the IWF device 18 directs the associated connection through the LANinterface. The asterisks in the first row indicate that the source IPaddress and port information do not affect the forward to interface whenthe destination IP data indicates a local or private IP address.

As indicated by the second row of Table 5, when data is received at theTCP/UDP port and provides that the destination IP address is thedestination end-system 20 and the source IP address is the originatingend-system 10, the IWF device 18 directs the connection to the newshort-cut SVC through the WAN interface, identified by an associated VPIand VCI. As indicated by the asterisks in the third row of Table 5,incoming data directed to a port other than the TCP/UDP port, orindicating destination and source IP addresses other than thedestination end-system 20 and the originating end-system 20,respectively, invokes the default ATM connection of the WAN interface.

Similarly, the IWF device 12 creates an entry in its forwarding tableindicating the successful set up of the ATM SVC, an example of which isshown in Table 6.

TABLE 6 Forward to Destination IP Source IP Port Interface Any localor * * LAN private address originating end- destination TCP/UDP WAN—newQoS system 10 end-system 20 port SVC * * * WAN—default ATM connection

The IWF device 18 also forwards the RESV message to the proxy server 30at step 652. The proxy server accepts the RESV message on behalf of thedestination end-system 20 at step 654. A short-cut IP connection at therequested QoS is then available over the newly established SVC betweenthe IWF device 12 and the IWF device 18, enabling communication betweenthe originating end-system 10 and the destination end-system 20,indicated at step 656. After the short-cut is established and availableat step 656, the QoS IP session is moved from the IP network 6 to thenew SVC based QoS short-cut in the ATM network. In other words, as inthe embodiment involving an RSVP capable destination end-system 20, theIP traffic travels the dedicated QoS short-cut path between theoriginating end-system 10 and the destination end-system 20 through theATM switches 22 and 24, as opposed to the hop-by-hop default IP paththrough the IP routers 14 and 16.

Although the invention has been described with reference to severalexemplary embodiments, it is understood that the words that have beenused are words of description and illustration, rather than words oflimitation. Changes may be made within the purview of the appendedclaims, as presently stated and as amended, without departing from thescope and spirit of the invention in its aspects. Although the inventionhas been described with reference to particular means, materials andembodiments, the invention is not intended to be limited to theparticulars disclosed; rather, the invention extends to all functionallyequivalent structures, methods, and uses such as are within the scope ofthe appended claims.

In accordance with various embodiments of the present invention, themethods described herein are intended for operation as software programsrunning on a computer processor. Dedicated hardware implementationsincluding, but not limited to, application specific integrated circuits,programmable logic arrays and other hardware devices can likewise beconstructed to implement the methods described herein. Furthermore,alternative software implementations including, but not limited to,distributed processing or component/object distributed processing,parallel processing, or virtual machine processing can also beconstructed to implement the methods described herein.

It should also be noted that the software implementations of the presentinvention as described herein are optionally stored on a tangiblestorage medium, such as: a magnetic medium such as a disk or tape; amagneto-optical or optical medium such as a disk; or a solid statemedium such as a memory card or other package that houses one or moreread-only (non-volatile) memories, random access memories, or otherre-writable (volatile) memories. A digital file attachment to email orother self-contained information archive or set of archives isconsidered a distribution medium equivalent to a tangible storagemedium. Accordingly, the invention is considered to include a tangiblestorage medium or distribution medium, as listed herein and includingart-recognized equivalents and successor media, in which the softwareimplementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the invention is not limited to such standards andprotocols. Each of the standards for Internet and other packet-switchednetwork transmission (e.g., TCP/IP, UDP/IP, RSVP, MPLS) and publictelephone networks (ATM, DSL) represent examples of the state of theart. Such standards are periodically superseded by faster or moreefficient equivalents having essentially the same functions.Accordingly, replacement standards and protocols having the samefunctions are considered equivalents.

1. A method for establishing an Internet protocol (IP) connectionthrough a switched transport network, between an originating host deviceand a destination host device communicating through an IP network, thedestination host device being incapable of resource reservation protocol(RSVP) signaling, the method comprising: associating a switchedtransport network address of a destination bridging device with an IPaddress of the destination bridging device, without communicating withan address server, in response to an RSVP path message initiated by anRSVP capable proxy device in association with the destination hostdevice, the RSVP path message being directed to the originating hostdevice through the IP network; and establishing the IP connection,through the switched transport network and the destination bridgingdevice, in response to a setup message directed to the switchedtransport network address of the destination bridging device.
 2. Themethod for establishing the IP connection according to claim 1, the RSVPpath message containing at least one quality of service parameter, whichis passed to the setup message, wherein the IP connection is establishedin accordance with the at least one quality of service parameter.
 3. Themethod for establishing the IP connection according to claim 1, theswitched transport network comprising an asynchronous transfer mode(ATM) network.
 4. The method for establishing the IP connectionaccording to claim 3, each IP connection comprising a switched virtualcircuit connection.
 5. The method for establishing the IP connectionaccording to claim 1, the switched transport network comprising amulti-protocol label switching (MPLS) network.
 6. The method forestablishing the IP connection according to claim 1, the setup messagecomprising a user-to-network interface protocol message.
 7. A method forimplementing an Internet protocol (IP) connection, through a switchedtransport network, between an originating host device and a destinationhost device, connected through an IP network, the destination hostdevice being incapable of resource reservation protocol (RSVP)signaling, the method comprising: communicating a request for the IPconnection to an RSVP capable proxy signaling device associated with thedestination host device; inserting a switched transport network addressof a destination bridging device into a first data field of an RSVP pathmessage received from the proxy signaling device; forwarding the pathmessage to an originating bridging device, through at least one routerin the IP network by default routing, the at least one router passingthe path message without modifying the first data field; forwarding asetup message to the destination bridging device, through at least oneswitching device in the switched transport network, based on thedestination bridging device address retrieved from the first data field,the setup message including an RSVP reservation request messagegenerated in response to the path message; and establishing the IPconnection between the originating host device and the proxy signalingdevice, through the originating bridging device and the destinationbridging device in response to the setup message, the proxy signalingdevice interfacing with the destination host device.
 8. The method forimplementing the IP connection according to claim 7, further comprising:including at least one quality of service connection parameter in asecond data field of the path message received from the proxy signalingdevice; including the second data field in the responsive reservationrequest message; and establishing the IP connection in accordance withthe at least one quality of service connection parameter.
 9. The methodfor implementing the IP connection according to claim 8, the at leastone quality of service connection parameter comprising a bandwidth. 10.The method for implementing the IP connection according to claim 7,further comprising: capturing the path message at the originatingbridging device and storing the address of the first bridging devicefrom the RSVP extension object in association with an address of thedestination host device, provided by the proxy signaling device;retrieving the stored address of the destination bridging device basedon the address of the destination host device included in the responsivereservation request message; and forwarding the setup message to thedestination bridging device based on the retrieved address.
 11. Themethod for implementing the IP connection according to claim 7, theswitched transport network comprising an asynchronous transfer mode(ATM) network.
 12. The method for implementing the IP connectionaccording to claim 11, the short-cut connection comprising a switchedvirtual circuit.
 13. The method for implementing the IP connectionaccording to claim 7, the switched transport network comprising amulti-protocol label switching (MPLS) network.
 14. A method forproviding a guaranteed quality of service Internet protocol (IP)session, through an asynchronous transfer mode (ATM) network, between anoriginating end-system and a destination end-system that is incapable ofresource reservation protocol (RSVP) signaling, the destinationend-system interfacing with an RSVP capable proxy device, the methodcomprising: establishing an initial IP session between the originatingend-system and the destination end-system through an IP network;receiving an RSVP path message from the proxy device, on behalf of thedestination end-system, at a destination interworking function (IWF)device, the path message including at least one parameter defining thequality of service; inserting an ATM address of the destination IWFdevice into a transport network hop (THOP) extension object of the pathmessage; forwarding the path message through the IP network by defaultrouting to an originating IWF device without modifying the THOPextension object; caching the THOP extension object in association withan IP address of the destination end-system; launching a setup messagethrough the ATM network based on the associated THOP extension objectand the IP address of the destination end-system, the setup messageincluding a responsive RSVP reservation request message, containing theat least one parameter defining the quality of service; receiving thesetup message at the destination IWF device and establishing a switchedvirtual circuit (SVC) connection between the destination IWF device andthe originating IWF device in accordance with the at least one qualityof service parameter; forwarding the reservation request message to theproxy signaling device, which accepts the reservation request message onbehalf of the destination end-system; and shifting the initial IPsession between the originating end-system and the destinationend-system to the SVC connection.
 15. The method for providing theguaranteed quality of service Internet session, according to claim 14,in which the default routing comprises best effort routing among IProuters.
 16. A system for establishing an Internet protocol (IP)connection between an originating host device and a destination hostdevice through a switched transport network, the destination host devicebeing incapable of resource reservation protocol (RSVP) signaling, thesystem comprising: an RSVP capable proxy device that interfaces with thedestination host device to provide RSVP signaling; and an originatingbridging device that associates a switched transport network address andan IP address of a destination bridging device, without communicatingwith an address server, in response to an RSVP path message, initiatedby the proxy device and received by the originating host device throughan IP network, the originating bridging device responding with a setupmessage directed through the switched transport network to the switchedtransport network address of the destination bridging device; whereinthe IP connection is established, through the switched transport networkand the proxy device, in response to the setup message.
 17. The systemfor establishing the IP connection according to claim 16, the setupmessage including at least one predetermined bidirectional flowparameter received from the path message, wherein the IP connection isestablished in accordance with the at least one bidirectional flowparameter.
 18. The system for establishing the IP connection accordingto claim 16, the switched transport network comprising one of anasynchronous transport mode (ATM) network and a multi-protocol labelswitching (MPLS) network.
 19. A system for establishing an Internetprotocol (IP) connection between an originating end-system and adestination end-system through a switched transport network, thedestination end-system being incapable of resource reservation protocol(RSVP) signaling, the system comprising: a proxy signaling device thatinterfaces with the destination end-system; a first interworkingfunction (IWF) device that inserts its switched transport networkaddress into a first data field of an RSVP path message, received fromthe proxy signaling device, and forwards the path message through atleast one router in an IP network by default routing, the at least onerouter passing the path message without modifying the first data field;and a second IWF device that receives the path message and forwards asetup message to the first IWF device through at least one switchingdevice in the switched transport network, based on the first IWFdevice's address retrieved from the first data field of the pathmessage, the setup message including an RSVP reservation request messagegenerated in response to the path message; wherein the IP connection isestablished between the originating end-system and the destinationend-system, through the first bridging device, the second bridgingdevice and the proxy signaling device, in response to the setup message.20. The system for establishing the IP connection according to claim 19,wherein at least one quality of service connection parameter is includedin a second data field of the path message and passed to the reservationrequest message included in the setup massage; and wherein the IPconnection is established in accordance with the at least one quality ofservice connection parameter.
 21. The system for establishing the IPconnection according to claim 20, the at least one quality of serviceconnection parameter comprising a bandwidth.
 22. A system for providinga guaranteed quality of service Internet protocol (IP) session, throughan asynchronous transfer mode (ATM) network, between an originatingend-system and a destination end-system that is incapable of resourcereservation protocol (RSVP), signaling, the originating end-system andthe destination end-system having an initial IP connection, the systemcomprising: a proxy signaling device that interfaces with thedestination end-system and launches an RSVP path message, including atleast one parameter defining a predetermined quality of service and atransport network hop (THOP) extension object; a first interworkingfunction (IWF) device that inserts its ATM address into the THOPextension object of the path message, received from the proxy signalingdevice, and forwards the path message through at least one router in anIP network by default routing, the at least one router passing the pathmessage without modifying the THOP extension object; and a second IWFdevice that receives the path message and launches a setup message tothe first IWF device through at least one switch in the ATM network,based on the ATM address in the THOP extension object, the setup messageincluding a responsive RSVP reservation request message, including theat least one parameter defining the quality of service; wherein aswitched virtual circuit (SVC) connection is established between thefirst IWF device and the second IWF device in accordance with the atleast one quality of service parameter, in response to the setupmessage; and wherein the reservation request message is forwarded to theproxy signaling device, which accepts the reservation request message onbehalf of the destination end-system, so that the initial IP sessionbetween the originating end-system and the destination end-system isimplemented over the SVC connection.
 23. A tangible computer readablemedium that stores a computer program, executable by a computer, forenabling an Internet protocol (IP) connection across a switchedtransport network between an originating host device and a destinationhost device, through a first bridging device and a second bridgingdevice, the destination host device being incapable of resourcereservation protocol (RSVP) signaling, the computer readable mediumcomprising: a first path message code for receiving a first path messagesignal from a proxy signaling device connected to the destination hostdevice, the first path message signal including an address parameter forthe second bridging device and an IP address of the proxy signalingdevice; a second path message code for forwarding a second path messagesignal through an IP network without modification to the addressparameter, the second path message signal including a switched transportnetwork address of the second bridging device in the address parameterand the IP address of the proxy signaling device; a reservation requestmessage code for receiving a second path message signal by the firstbridging device in response to the second path message, the reservationrequest message signal including the IP address of the proxy signalingdevice; a first setup message code for forwarding a first setup messagesignal through the switched transport network to the transport networkaddress of the second bridging device, retrieved from the second pathmessage signal, the first setup message signal including the reservationrequest message signal; and a second setup message code for forwarding asecond setup message signal to the IP address of the proxy signalingdevice, the second setup message signal including the reservationrequest message signal, the IP connection being established in responseto the second setup message signal.
 24. The tangible computer readablemedium according to claim 23, the first path message signal, the secondpath message signal and the reservation request message signal furtherincluding a bidirectional flow parameter that defines at least onepredetermined quality of service attribute of the IP connection, whereinthe IP connection is established in accordance with the quality ofservice attribute.
 25. The tangible computer readable medium accordingto claim 24, wherein the at least one quality of service attributecomprises a bandwidth.
 26. The tangible computer readable mediumaccording to claim 23, the first path message signal, the second pathmessage signal and the reservation request message signal furtherincluding a reverse charging parameter, wherein accounting data for theIP connection is associated with the originating host device when thereverse charging parameter is activated.
 27. The tangible computerreadable medium according to claim 26, wherein the accounting data forthe IP connection is associated with the destination host device whenthe reverse charging parameter is not activated.
 28. The tangiblecomputer readable medium according to claim 23, the first path messagesignal, the second path message signal and the reservation requestmessage signal complying with a resource reservation protocol (RSVP).29. The tangible computer readable medium according to claim 23, thefirst setup message signal and the second setup message signal complyingwith a user-to-network interface (UNI) protocol.
 30. The tangiblecomputer readable medium according to claim 28, the switched datatransport network comprising an asynchronous transport mode (ATM)network.
 31. The tangible computer readable medium according to claim28, the switched data transport network comprising a multi-protocollabel switching (MPLS) network.